I like it! @scotthovestadt are we gonna make any more 24 releases, or can we start breaking things?

Codecov Report

Merging #8455 into master will decrease coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8455      +/-   ##
==========================================
- Coverage   63.46%   63.38%   -0.09%     
==========================================
  Files         274      274              
  Lines       11385    11341      -44     
  Branches     2771     2760      -11     
==========================================
- Hits         7226     7188      -38     
+ Misses       3546     3541       -5     
+ Partials      613      612       -1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b76f01b...c46a83d. Read the comment docs.

Can you update @babel/preset-env target as well?

https://github.com/facebook/jest/blob/f4c6e318a360048982e89439c1329e8fc6b857de/babel.config.js#L31

Two failing snapshots due to changed stack trace (removed async await transpilation, I guess). Mind updating them? 🙂

@SimenB Done

One of the CI steps is failing as the process runs out of memory. As far as I can see there's 4096 MBs available in CircleCI, so we can bump it a little: NODE_OPTIONS=--max_old_space_size=4096. Obviously there are some other processes and the operating system consuming some memory too, so we'll never reach 4096, but this setting will allow all remaining memory to be consumed.

One of the CI steps is failing as the process runs out of memory. As far as I can see there's 4096 MBs available in CircleCI, so we can bump it a little: NODE_OPTIONS=--max_old_space_size=4096. Obviously there are some other processes and the operating system consuming some memory too, so we'll never reach 4096, but this setting will allow all remaining memory to be consumed.

This test fails on master for a long time.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.